-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
waitFor return check since waitForText doesn't assert #146
base: 8.3.x
Are you sure you want to change the base?
Conversation
*/ | ||
public function registerFunctionNames() | ||
{ | ||
return ['waitForText']; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add more of the waitFor* methods?
Nice one @smmccabe - this is looking pretty good and very useful. One small question about whether to include the other waitFor* methods. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, makes sense in general to me. Can we add some safe guards that we do not trigger on the function call waitForText() and that we are in a test class?
I feel like this check would be a better fit for drupalcheck, which can do real semantic analysis with phpstan https://github.com/mglaman/drupal-check
@@ -0,0 +1,57 @@ | |||
<?php | |||
/** | |||
* Unit test class for the DbQuery sniff. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
copy paste leftover?
Improved version of #145 which was initially only internal. The one has test and matches code standards